Scawen tried to help you, doesn't that mean he takes it seriously? We're just trying to figure out what the issue is. You aren't the only one having troubles with the unlock code. Please be patient.
This has caught me off guard as well. The "Unlock" button must remain active for non-S3 users who may buy a higher license in the future and need to unlock it again. Once an S3 user unlocks their LFS, that but doesn't make much sense to me, but I may be missing something.
Perhaps the user could automatically get back to the entry screen after confirming the dialog "username and pass confirmed"?
Do you want less security of people's LFS accounts and a bigger probability of them being hijacked and stolen in case of another 3rd party site data leak?
Your post adds no value, at least add some reasoning to your claim.
I think this is a good point. Scawen did try to make it visible by adding a fake event into the LFS calendar. What about sending out newsletter emails after such an important change? Or is that planned only after a new official patch?
Someone correct me if I'm wrong, but as far as I'm aware, the e-mail address has been a mandatory field when creating a new LFS account for many years. I remember entering it when I created my account in 2007.